A Distributed Version Control System (DVCS) differs from legacy centralized systems because there is no single central repository that Git forces everyone to rely upon. Instead, every developer possesses a full backup of the project’s entire history.
1. The Distributed Advantage
In this model, every node is technically equal. However, we designate one specific node as the official repository to maintain project standards. This necessitates an Integrator—a role responsible for managing how contributions from various local environments flow into the public sphere.
2. Secure Access Protocols
Integrity is maintained through specific transport layers:
- HTTPS (or SSH): Lets you fetch or push, but requires a password. This prevents unknown developers from overwriting commits.
- HTTP: Fetching over HTTP requires no credentials, allowing open read-access for anyone without compromising the security of the write-access.
3. Role of Bitbucket
Bitbucket is a DVCS hosting provider that makes it very easy to set up a Git repository and start collaborating with a team. It acts as the public gateway for your distributed workflow.